Systems, methods, and apparatus to monitor mobile internet activity

ABSTRACT

Systems, methods, and apparatus to monitor mobile Internet activity are disclosed. An example system includes at least one processor, and memory including instructions, when executed, cause the at least one processor to in response to obtaining first panelist demographic information associated with a first panelist and second panelist demographic information associated with a second panelist, assign a first port of a proxy server to a first mobile device associated with the first panelist and a second port of the proxy server to a second mobile device associated with the second panelist, the first port different from the second port, transmit configuration information to the first mobile device to instruct the first mobile device to transmit requests for media including a first request to the first port, and in response to obtaining the first request at the first port, store an association between the first panelist demographic information and the media.

RELATED APPLICATION

This patent arises from a continuation of U.S. patent application Ser.No. 14/537,488, which was filed on Nov. 10, 2014, and issued on Jun. 11,2019, as U.S. Pat. No. 10,320,925, which is a continuation of U.S.patent application Ser. No. 12/856,651, which was filed on Aug. 14,2010, and issued on Nov. 11, 2014, as U.S. Pat. No. 8,886,773. U.S.patent application Ser. No. 14/537,488 and U.S. patent application Ser.No. 12/856,651 are hereby incorporated herein by reference in theirentireties.

FIELD OF THE DISCLOSURE

This disclosure relates generally to monitoring Internet activity and,more particularly, to systems, methods, and apparatus to monitor mobileInternet activity.

BACKGROUND

In recent years, methods of accessing Internet content have evolved. Forexample, Internet content was formerly primarily accessed via computersystems such as desktop and laptop computers. Recently, handheld mobiledevices (e.g., smartphones) have been introduced that allow users torequest and view Internet content. Typically, but not always, mobiledevices request and receive Internet content via a wireless accessnetwork such as a cellular network.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an example system to monitor mobileInternet activity.

FIGS. 2 and 2A are a block diagrams illustrating an example request andresponse flow through the example system of FIG. 1.

FIG. 3 is a block diagram of the example proxy of FIG. 1.

FIG. 4 is a flowchart representative of example machine-readableinstructions that may be executed to implement the example proxy ofFIGS. 1, 2, and 3.

FIG. 5 is a flowchart representative of example machine-readableinstructions that may be executed to implement the example registrar ofFIG. 1.

FIG. 6 illustrates an example configuration file that may be generatedby the example registrar of FIG. 1.

FIG. 7 is a block diagram of an example computer that may execute, forexample, the machine-readable instructions of FIGS. 4 and/or 5 toimplement the example monitor of FIGS. 1, 2, and 3, and/or the exampleregistrar of FIG. 1.

DETAILED DESCRIPTION

Mobile monitoring companies desire to gain knowledge on how usersinteract with their handheld mobile devices such as smartphones. Inparticular, the mobile monitoring companies want to monitor Internettraffic to and/or from the handheld mobile devices to, among otherthings, monitor exposure to advertisements, determine advertisementeffectiveness, determine user behavior, identify purchasing behaviorassociated with various demographics, etc. Some known systems haveutilized a proxy server to monitor Internet content being transmitted toand from the monitored device.

Such known monitoring systems implemented the proxy server as an HTTPproxy that communicated with monitored handheld devices via a singleport and required the monitored devices to provide authenticationcredentials including a username/device name and password that uniquelyidentified the mobile device involved in this Internet communication.These monitoring systems allowed mobile monitoring companies toassociate Internet activity with the mobile device it originated frombased on the username and password. Internet activity on handheld mobiledevices is not limited to use of browsers (e.g., Apple® Safari®). Forexample, the Apple® iPhone® and the Apple® iPad™ support many thirdparty applications (sometimes referred to as “Apps”) accessing Internetcontent to perform a special function. For example, a weatherapplication may request and display HTTP data from www.weather.com.These apps typically do not permit unrestricted browsing from website towebsite on the Internet (although they may permit movement within adefined set of webpages). Thus, apps typically provide access to alimited set of data on the Internet. In contrast, a browser enables auser to access virtually any publicly available site on the Internet(subject to restrictions such as content blockers) and directly showsthe user the contents a website such as www.weather.com.

While some applications accessing Internet content properly respond toproxy requests to provide credentials, many applications, such as theweather application from the previous example, do not presently supportproxy authentication and therefore fail to function if a proxy requestscredentials. This can be frustrating for panelists and may cause thepanelist to abandon participation in the monitoring panel. Furthermore,it is desirable for monitoring entities to monitor Internet activitywithout affecting the manner in which users behave. Causing applicationfailure due to a monitoring technique is inconsistent with that desire.

To avoid errors inherent in using an authenticated proxy, the examplesystem shown in FIG. 1 employs an un-authenticated proxy. Use of a proxythat does not request authentication credentials (i.e., anun-authenticated proxy), is problematic in that such an approach doesnot lend itself to user identification, and user identification isnecessary to correlate activity behavior with demographics. The examplesystem of FIG. 1 addresses this problem by hosting a uniqueun-authenticated port for each panelist and/or mobile device andinstructing each monitored mobile device to communicate using itsuniquely assigned port. This use of multiple ports allows the monitoringentity to uniquely associate the Internet traffic it detects with thepanelist and/or mobile device involved in such traffic. While previousmonitoring systems hosted a proxy connection on a single port such asport 8080, the proposed monitoring system hosts connections on manyavailable ports (e.g., ports 0 to 65535). Certain ports are omitted fromthe list of available ports if those ports are associated with otherInternet services. For example, ports 0 through 1023 are defined as WellKnown Ports by the Internet Assigned Numbers Authority (IANA), and areprohibited from use without registration. Thus, Well Known Ports are notused in the example system of FIG. 1.

The example monitoring system of FIG. 1 records the identifications ofdata that the client devices request and/or receive and/or some or allof the data itself. Identifications of data and/or the data itself(e.g., web content) is collectively referred to herein as “sessiondata.” The session data is recorded in association with the panelist viathe port number on which the session data is transmitted. From therecorded session data and the port number, the monitoring system canuniquely identify the site(s) that a particular panelist is visiting andhow the panelist interacted with their mobile device, while avoidinginterruption of services for the panelist.

FIG. 1 is a block diagram of an example system 100 to monitor mobileInternet activity. The example system monitors Internet traffic toand/or from handheld mobile devices (e.g., a first client device 110associated with a first panelist 115, a second client device 130associated with a second panelist 135). The monitored Internet trafficbetween the monitored devices (e.g., the client device 110, and theclient device 130) and Internet sites (illustrating Internet contentprovider(s) 170) is routed to the example monitoring system 100. Asshown in FIG. 1, the traffic passes through a wireless (e.g., cellular)communication system (e.g., an Internet service provider 145 andcommunicative links 120, 140). The example monitoring system 100includes a registrar 155, a storage database 160, and a proxy 165.

The example first and second client devices 110, 130 of FIG. 1 arehandheld mobile devices. While in the illustrated example the firstclient device 110 is shown as an Apple® iPhone® and the second clientdevice 130 is shown as a flip phone, any other type of device may beused. For example, other types or phones, a laptop computer, a desktopcomputer, a personal digital assistant (PDA), a netbook, or a tabletcomputer (e.g., an Apple® iPad™) may additionally or alternatively beused. The first and second client devices 110, 130 may implement anymobile operating system, and may implement any type of hardware and/orform factor. In the illustrated example, the first and second clientdevices 110, 130 are mobile devices and communicate via the first andsecond wireless communication links 120, 140.

The first and second communication links 120, 140 of the illustratedexample are cellular communication links. However, any other methodand/or system of communication may additionally or alternatively be usedsuch as, for example, an Ethernet connection, a Bluetooth connection, aWiFi connection, etc. Further, the example first and secondcommunication links 120, 140 of FIG. 1 implement a cellular connectionvia a Global System for Mobile Communications (GSM). However, any othersystems and/or protocols for communications may be used such as, forexample, Time Division Multiple Access (TDMA), Code Division MultipleAccess (CDMA), Worldwide Interoperability for Microwave Access (WiMAX),Long Term Evolution (LTE), etc. When alternative communication methodsand/or systems are used (e.g., WiFi), the topology of the communicationsystem may include a firewall that blocks Internet communications usingcertain ports. When the port uniquely assigned to a panelist is blockedby the firewall, the client device may fail to operate as expectedand/or present error messages to the panelist.

The first and second panelists 115, 135 of the illustrated example arepanelists participating in a monitoring service. Although the examplesystem of FIG. 1 is a panelist-based system, non-panelist and/or hybridpanelist systems may alternatively be employed. In the panelist systemof the illustrated example, demographic information is obtained from theuser when the user joins and/or registers for the panel. The demographicinformation may be obtained from the user via a telephone interview, byhaving the user complete an online survey, etc. Additionally oralternatively, panelists may be contacted and/or enlisted using anydesired methodology (e.g., random selection, statistical selection,phone solicitations, Internet advertisements, surveys, advertisements inshopping malls, etc.).

In the illustrated example, the first and second panelists 115, 135 areassociated with the first and second client devices 110, 130,respectively. In the illustrated example, the client devices 110, 130are owned, leased, or otherwise belong to their respective panelists.The monitoring entity of the illustrated example does not provide theclient devices. In other systems, panelists may be provided with clientdevices to participate in the panel. While in the illustrated example,the first and second client devices 110, 130 are each associated with asingle panelist, the first and second client devices 110, 130 mayalternatively be associated with more than one panelist. For example, afamily may have a single client device that may be shared amongstmultiple users. The sharing of a client device is less common when theclient device is a cellular phone than when the client device is aportable computer (e.g., an Apple® iPad™).

The Internet service provider 145 of the illustrated example provideswireless Internet service to the first and second client devices 110,130 via the communication links 120, 140. In the illustrated example,the wireless service is provided via a cellular connection. However, theInternet service provider 145 may provide Internet service via any othertype of connection. Further, the Internet service provider 145 mayimplement the cellular connection via a Global System for MobileCommunications (GSM). However, any other systems and/or protocols forcommunications may be used. In practice, the Internet service provider145 is sometimes referred to as a carrier, and provides a access tocarrier network to the client devices.

In the illustrated example, the monitoring system 100 is shown asmultiple computing systems. However, the monitoring system 100 mayultimately be comprised of a single computing system. In the illustratedexample, the monitoring system 100 includes the registrar 155, thestorage database 160, and the proxy 165. However, additional structuresmay be implemented to carry out one or more portions of thefunctionalities implemented by the registrar 155, the storage database160, and/or the proxy 165, and/or other functions.

In the example of FIG. 1, the registrar 155 receives registrationinformation from the panelists 115, 135 and stores a record identifyingthe panelist 115, 135 and/or their respective client devices 110, 130.In the illustrated example, the record identifying the panelist 115, 135is the port number assigned to the panelist (e.g., the port assigned tothe panelist may be 50,000 and the record identifying the panelist maybe 50,000). In the illustrated example, the received registrationinformation includes demographic information. However, any otherinformation may additionally or alternatively be collected. Theregistration information may include, for example, informationidentifying the model of mobile device associated with the panelist, amailing address associated with the panelist, an email addressassociated with the panelist, a phone number associated with the mobiledevice, a unique identifier of the panelist and/or mobile device (e.g.,a social security number of the panelist, a phone number of the mobiledevice, a zip code of the panelist, and/or any combination or derivationof any information related to the panelist and/or mobile device), theage of the panelist, the gender of the panelist, the race of thepanelist, the marital status of the panelist, the income of the panelistand/or the household of the panelist, the employment status of thepanelist, where the panelist typically intend to use their device, howlong the panelist has owned their device, the education level of thepanelist and/or any other information related to the panelist or themobile device.

In the illustrated example, the registration data is received by theregistrar 155 via an electronic interface (e.g., by a panelist enteringdata into a form at a website or answering survey questions at awebsite). However, the registrar may receive the registration data mayvia other means. For example, the registrar may receive the registrationdata via a personal interview (by telephone or in person), a telephoneinterface, direct mailing, purchased lists, etc. While the registrar 155of the illustrated example is an electronic system, the registrar 155may alternatively be implemented manually by a person or group of peoplecollecting and entering the registration data into the storage database160.

Upon receiving the registration data, the registrar 155 of theillustrated example creates a record associating the panelist and adevice identifier information with the collected demographicinformation. The registrar 155 may also assign a unique alphanumericidentifier to the panelist or device. The identifier may be based on,for example, a serial number of the client device. The record is storedin the storage database 160. In the illustrated example, the registrar155 also assigns a unique port number to the panelist 115, 135 and/orthe client device 110, 130 and stores the port number in the record (orin association with the record for that panelist and/or client device).As noted above, in addition to assigning and storing the port number,the registrar may assign and store additional identifiers. For example,the registrar may assign and store an identifier of the client deviceand/or the panelist. The panelist or client device identifier(s) may bethe same as the port number, or they may be different from the portnumber.

In addition to assigning and storing the port number, the registrar 155of the illustrated example generates a configuration document. In theillustrated example, the configuration document is an Extensible MarkupLanguage (XML) file implementing a property list (referred to herein asa plist) file comprising configuration data such as the port number andan Internet proxy address to be used by the corresponding panelistand/or client device. However, any other type of document may begenerated such as, for example, a comma separated (CSV) document, aPortable Document Format (PDF) document, a Microsoft® Word® document,etc. In the illustrated example, the configuration document is signedusing a public/private key infrastructure. For example, theconfiguration document may be signed via a digital certificate. However,the configuration may alternatively not be signed. If the configurationdocument is not signed, it may appear as an invalid configuration fileto the panelist, which may cause the panelist to abandon participationin the panel. The configuration file is sent to the corresponding clientdevice (e.g., via an email message with the file attached or with a linkto the file). The client device then interprets the data in theconfiguration file, thereby applying the data (e.g., the port number andInternet proxy address) to future communication of the mobile device. Inthe illustrated example the configuration file causes the mobile deviceto send all Internet traffic to the Internet address of the proxy 165and to specify the unique port number assigned to the client device insuch communication. As a result, all Internet communications to and/orfrom the mobile device are addressed to a uniquely assigned port of theproxy 165 and can, thus, be identified or associated with thatparticular client device. In the illustrated example the plist file isimplemented for interpretation by an Apple® iPhone® and/or an Apple®iPad™. However, the mobile device may be any other type of mobiledevice. Further, the configuration file may be custom generated for theparticular type of mobile device based on the model of the mobile deviceidentified to (or by) the registrar as part of the registration data.

While in the example of FIG. 1, the document is an electronic documentthat may be interpreted by the client device to automatically configurethe client device to communicate Internet related messages to a uniqueport of the proxy 165, the document may additionally or alternativelycomprise an instruction document that may guide the panelist on how toconfigure the client device to communicate with the proxy. Theinstruction document may thereby instruct the panelist on how to applythe configuration file or may instruct the panelist on how to directlyapply the data stored in the configuration file to the client device.

As noted above, the registrar 155 transmits the configuration documentto the panelist and/or client device. In the illustrated example, theconfiguration file is provided via an electronic mail (email) message.The email message includes a hyperlink to download the configurationfile to the client device. However, any other methods of transmittingthe configuration file may additionally or alternatively be used. Forexample, the configuration file may be transmitted as an attachment tothe email message, the registrar 155 may transmit a short messageservice (SMS) message comprising a link to or a textural representationof an Internet address where the client device may download theconfiguration file, a direct mailing may be sent to the panelistcomprising the instruction document and/or additionally comprising anelectronic medium containing the configuration file, a telephone callmay be placed to orally instruct the panelist on how to configure theclient device, etc.

The registrar 155 of FIG. 1 is implemented by a processor executinginstructions, but it could alternatively be implemented by an ASIC, DSP,FPGA, or other circuitry. The storage database 160 receives and storesidentifiers associating the panelists 115, 135 with the client devices110, 130 from the registrar 155. Additionally, the storage database 160receives and stores monitoring data from the proxy 165. The monitoringdata is associated with the corresponding panelist and/or client devicevia the port number used for the corresponding monitored Internettraffic. The storage database 160 may also be capable of storing datathat is not identifiers and/or measurement data. For example, updatedsoftware and/or updated firmware for any component of the monitoringsystem 100 may be stored in the storage database 160. Further, thestorage database 160 may be capable of storing information that enablesthe registrar 155 to generate the configuration document. For example,the storage database 160 may store registration information such as themodel of the client device 110, 130. Additionally, the storage database160 may store demographic data as collected by the registrar 155.

The storage database 160 may be any device for storing data such as, forexample, flash memory, magnetic media, optical media, etc. Furthermore,the data stored in the storage database 160 may be in any data formatsuch as, for example, binary data, comma delimited data, tab delimiteddata, structured query language (SQL) structures, etc. While in theillustrated example the storage database is illustrated as a singledatabase, the storage database 160 may be implemented by multipledatabases.

The proxy 165 of the illustrated example receives requests from theclient devices 110, 130 via the wireless Internet service provider 145.The requests of the client devices 110, 130 are received by the proxy165 due to the configuration file having been applied to respective onesof the client device instructing the client device to transmit allsubsequent requests through the proxy 165. The proxy 165 is located atthe Internet proxy address identified in the configuration file, andreceives request via ports associated with client devices. In theillustrated example, the ports are Dynamic and/or Private Ports asdefined by the Internet Assigned Numbers Authority (IANA). Therefore,the range of assignable ports used by the illustrated proxy 165 forInternet traffic with monitored client devices is 49152 through 65535.By only using Dynamic and/or Private Ports, the group of panelistsserved by a single proxy 165 is effectively limited to 16383 clientdevices. This size can be expanded by using additional proxies at otherInternet addresses. The additional proxies at other Internet addressesmay be implemented by the same proxy 165 or by multiple proxies. Forexample, the proxy 165 may have multiple Internet addresses assigned toa network interface of the proxy 165 (e.g., virtual interfaces), or theproxy 165 may have multiple network interfaces each having an Internetaddress. While in the illustrated example only ports used within theDynamic and/or Private Ports range are used, any other ports mayadditionally or alternatively be used. For example, ports within theRegistered Ports range and/or the Well Known Ports range may potentiallybe used to increase the group of panelists to as large as 65535panelists with a single proxy. In a scenario where a panel monitoringsystem such as the monitoring system 100 is being tested, a typically apanel will include at least sixty panelists and, thus, the proxy 165will use at least sixty ports (e.g., one for each panelist). In ascenario where an ongoing panel is used, a panel size of at least 1,500panelists may be used and, thus, the proxy 165 will use at least 1,500ports (e.g., one for each panelist).

Upon receiving a request from a client device 110, 130, the proxy 165retrieves the requested Internet content from the Internet contentproviders 170 (or from a local cache if, for example, it had previouslybeen requested and stored). In order to identify the panelist associatedwith the request, communication to and from each specific panelistoccurs over the uniquely assigned (e.g., dedicated) port. While thecommunication between a client device 110, 130 use the proxy 165 occursover a single port (e.g., the port assigned to that client device 110,130 by the registrar 155), communication between the proxy 165 and theInternet content providers 170 may be implemented over any port.Typically, the port used by the proxy to communicate with contentproviders 170 is limited to hypertext transfer protocol (HTTP) data thatoccurs over port 80. After retrieving the requested Internet contentfrom the Internet content provider(s) 170, in the illustrated examplethe content is relayed to the requesting client device 110, 130 via theassigned port. Additionally or alternatively, the content may be relayedto the requesting client device 110, 130 via a port other than theassigned port (e.g., port 80).

The proxy 165 of the illustrated example stores the requests forInternet content and/or portion(s) of such requests originating from theclient devices 110, 130 in the storage database 160 in association withthe port numbers over which the request was received. In storing therequests, the proxy 165 may additionally store other identifiers suchas, for example, the identifier of the client device 110, 130, and/orthe identifier of the panelist 115, 135. Additionally or alternatively,the proxy 165 may store a portion of the Internet content in the storagedatabase 160. For example, the proxy 165 may store the body of a webpagetransmitted to the client device 110, 130. In another example, the proxy165 may store an identifier of an advertisement appearing on the webpagetransmitted to the client. This is particularly useful in situationswhere advertisements are rotated at websites. Additionally oralternatively, the proxy 165 may store characteristics of the response,such as, for example the HTTP header, a status code of the HTTP header,a content type of the HTTP header, etc.

The Internet content providers 170 supply content to clients via theInternet. In the illustrated example, the proxy 165 acts as anintermediary for the client devices 110, 130, and, thus, is the clientof the Internet content providers 170. Internet content is oftensupplied over port 80, as most Internet content is in the form of HTTPdata. However, any other port may be used to supply Internet content.For example, file transfer protocol (FTP) data may be transmitted overport 21, HTTP over Secure Socket Layer (SSL) may be transmitted overport 443, etc.

The Internet content providers 170 can be any provider. For example, theInternet content providers 170 may comprise a web server hostingwebpages formatted as Hypertext Markup Language (HTML) content.Alternatively, the Internet content provider 170 may be an applicationserver providing application content to applications accessing Internetcontent. The application content may be formatted as HTML, XML, or mayuse any other protocol or port to return content to the requester. Insome examples, the application data is implemented in a protocolspecifically targeted for an application requesting Internet content(e.g., as the weather application described above).

FIG. 2 is a block diagram 200 illustrating an example request andresponse flow through the example system of FIG. 1. The block diagram200 of FIG. 2 illustrates communication between a mobile device 205, acarrier network 230, the proxy 165, the storage database 160, theInternet 240, and the Internet content providers 170. The mobile device205 represents either of the client devices 110, 130 and comprises adevice networking subsystem 210, a browser application 215, anapplication accessing Internet content 220, and a user interface 225.Additionally, the block diagram illustrates a first request 235, asecond request 245, a first response 250, and a second response 255.

The device networking subsystem 210 provides a framework fortransmitting and receiving content. The device networking subsystem 210may be implemented via an application processor, a software system thatfacilitates networked communication, a browser engine, a basebandprocessor that transmits network traffic, and/or any other system thatprovides a framework for transmitting and receiving content. In theillustrated example, the device networking subsystem is implemented bythe networking libraries provided in the Apple® iPhone® operatingsystem. However, any other libraries, systems, or programs mayadditionally or alternatively be used.

The browser application 215 and application accessing Internet content220 are applications that are executed by a processor of the mobiledevice 205. The browser application 215 requests HTTP Internet contentfrom Internet content providers 170, and renders the HTTP content fordisplay. Additionally or alternatively, the browser application mayrequest and render HTTPS Internet content. In some examples, the browserapplication is implemented by Apple® Safari®. However, any otherapplication may alternatively be used. For example, Pocket InternetExplorer may be used. In some examples, the HTTP Internet content isHTML content. However, the content may be presented in any format thatmay be rendered by the browser application 215.

The application accessing Internet content 220 may be any application onthe mobile device that requests Internet content. For example, theapplication accessing Internet content 220 may be a weather applicationaccessing Internet content provided by www.weather.com. The Internetcontent provider 170 providing content for www.weather.com may respondto content requests with HTML data. However, any other type of data maybe contained in the content request. For example, the Internet contentprovider 170 providing content for www.weather.com may provide an XMLfile containing a condensed weather forecast. Additionally oralternatively, the application accessing Internet content 220 mayrequest media such as, for example, photos, video, audio, etc.Typically, applications accessing Internet content 220 are limited to asmall amount of information to be displayed. For example, the weatherapplication may not be able to display sports news. Although the browser215 or the application accessing Internet content 220 may initiaterequests for content, in some devices, such as the Apple® iPhone®,requests are formatted and transmitted by the device networkingsubsystem 210 based on system wide settings that control routing and/oraddressing of such requests (e.g., to a specific port of a proxy 165).

The user interface 225 of the illustrated example provides a display tothe user and receives input from the user. The user interface 225 maycomprise hardware, a graphics library, and/or a graphics driver fordisplaying content to the panelist, and may comprise hardware, an inputlibrary, and/or an input driver for receiving input from the panelist.Either or both the browser application 215 and the application accessingInternet content 220 may utilize the user interface to display contentand receive input.

The carrier network 230 is hosted by the Internet service provider 145.In the illustrated example, the carrier network 230 is an InternetProtocol (IP) version 4 (IPv4) based network. However, any othernetworking technology may additionally or alternatively be implemented.For example, the carrier network may 230 implement the IP version 6(IPv6) protocol. Further, the carrier network 230 of the illustratedexample is implemented using communication links 120, 140. Whilecellular connections are shown, any other method of communication mayadditionally or alternatively be used such as, for example, an Ethernetnetwork, a WiFi network, etc. Additionally, the carrier network 230 isshown as a public network. However, the network may be a privatenetwork.

The proxy 165 receives a first request 235 for Internet content from themobile device, retrieves the content by sending a second request 245 tothe corresponding content provider 170, receive the content in a firstresponse 250 from the content provider 170, and relays the content tothe mobile device 205 via a second response 255. In the illustratedexample, the proxy 165 stores characteristics and/or identifiers of therequest and/or response in the storage database 160. Thesecharacteristics and/or identifiers may be, for example, a timestamp ofthe request and/or response, an IP address of the client, a user agentof the request, a status code of the response, a content type of theresponse, etc. However, the proxy 165 may additionally store theInternet content of the response in the storage database 160. Inrelaying the request, the proxy 165 translates the port of the requests,as is described below in conjunction with FIG. 2A.

The Internet 240 in the illustrated example is a public network.However, the a private network may instead be employed. For example, anetwork internal to an organization and/or company may be used todetermine how members of the organization and/or employees of thecompany utilize internal web content via mobile devices.

The illustrated example shows, a communication stream for a singlerequest. The first request 235 is transmitted to the proxy 165 from themobile device 205 over the carrier network 230. The first request 235uses the unique port assigned to the mobile device 205 (e.g., port50,000), and is for HTTP content (e.g., the request is for content thatis served over port 80). However, the content requested may be requestedover any port. For example, the request may be for file transferprotocol (FTP) content and may occur over port 21. The proxy 165, uponreceiving the first request 235, stores some or all of the request inthe storage database 160, and generates a second request 245. The secondrequest 245 is effectively a translation of the first address as shownin FIG. 2A. The second request is addressed to the Internet contentprovider 170 identified in the first request 235. The second request 245in the illustrated example is transmitted via the Internet 240 over port80, as the first request 235 identified content to be served over port80. The Internet content provider 170 responds to the second request 245with the first response 250. The proxy 165 receives the first response250 via port 80, stores some or all of the request in the storagedatabase 160, and forwards the content of the first response 250 as thesecond response 255 to the mobile device 205 over the port assigned tothe mobile device 205.

FIG. 2A is a block diagram 201 illustrating an example request andresponse flow through the example system of FIG. 1. The block diagram201 includes the proxy 165, the Internet content provider(s) 170, themobile device 205, the carrier network 230, and the Internet 240. Theblock diagram 201 additionally includes the first request 235, thesecond request 245, the first response 250, and the second response 255.Further, the requests and responses of the illustrated example arerepresented by HTTP request and response headers. The first request 235is represented by the first HTTP request header 236 and the secondrequest 245 is represented by the second HTTP request header 246. Thefirst response 250 is represented by the first HTTP response header 251and the second response 255 is represented by the second HTTP responseheader 256.

The first HTTP request header 236 is the header of a GET requestgenerated by the mobile device 205. In the illustrated example, theInternet content provider 170 is identified by the absolute UniformResource Locator (URL) identified in the first line of the first HTTPrequest header 236 and the address of the proxy 165 and uniquelyassigned port are identified by the “Host” line of the first HTTPrequest header 236. The host identified in the illustrated example isproxy.MonitoringEntity.com, and the port that the request was made on is50,000. However, any other address identifying the proxy 165, and anyother port may alternatively be used. For example, the addressidentifying the proxy 165 may be the Internet Protocol (IP) address ofthe proxy 165. In the illustrated example, the absolute URL of theInternet resource is “http://www.weather.com/home.html”. However, anyother URL may additionally or alternatively be used.

The proxy 165 receives the first content request 235 and generates thesecond content request 245. The second content request 245 isrepresented by the second HTTP request header 246. In the illustratedexample, the second HTTP request header 246 is a GET request directed to“http://www.weather.com”, and is transmitted over port 80 as no portother than port 80 is identified. The content being requested from“http://www.weather.com” in the illustrated example is “/home.html”. Theproxy generates the contents of the second request by inspecting thefirst request 235. For example, the proxy 165 identifies the requestedcontent of the first request 235 as “http://www.weather.com/home.html”,determines that the port to be translated to is port 80 (identified byhttp://), determines that the Internet content provider 170 identifiedis “www.weather.com”, and determines that the requested webpage from theInternet content provider is “/home.html”. The second content request245 is transmitted over port 80 because the proxy 165 determines thatthe requested content is HTTP content, and no alternative port number isspecified. Alternatively, the content identified by the first contentrequest 235 may be content that is provided on a port other than port80. In that example, the absolute URL of the first HTTP request header236 would identify the requested content as“http://www.weather.com:1234/home.html”, to convey that the contentidentified by the request is provided on port 1234. Further, the proxy165 would generate the second HTTP request header 246 and include port1234 in the identified host (e.g., www.weather.com:1234).

The Internet content providers 170 receive the second content request245, and respond to the request via the first response 250. The firstresponse 250 is transmitted to the proxy 165. In the illustratedexample, the first response is transmitted over port 80, as it is aresponse to a content request made on port 80. However, any other portmay be used to transmit the first response to the proxy 165. The proxy165 receives the first response 250, and determines the correct portthat the second response 255 should be transmitted over. In theillustrated example, the proxy 165 determines the port that the secondresponse should be transmitted over by associating the first response250 with the first request 235 via the second request 245. In such anexample, the proxy 165 can identify that the first request 235originated on port 50,000, and thus, the second response should betransmitted on port 50,000. However, any other method of determining theport to transmit the second response over may additionally oralternatively be used. Further, the response may be transmitted over aport other than the port assigned to the mobile device 205.

FIG. 3 is a block diagram of the example proxy 165 of FIG. 1. Theexample proxy 165 includes request and response ports 305, a requestservicer 310, an Internet content processor 315, a content gatherer 320,and an Internet port 325. The request and response ports 305 receiverequests and transmit responses to and/or from the client devices 110,130. The requests received by the ports 305 are passed to the requestservicer 310. The content gatherer 320 transmits requests and receivesresponses from the Internet content providers 170 via the Internet port325. The Internet content processor 315 stores the requests (or portionsthereof) and/or the retrieved content (or portions thereof oridentifiers associated therewith) in the storage database 160.

The request and response ports 305 of the illustrated example areTransmission Control Protocol (TCP) ports and/or User Datagram Protocol(UDP) ports. However, any other port-based system may additionally oralternatively be used. The request and response ports of the illustratedexample are Dynamic and/or Private Ports as defined by IANA. As such,the ports 305 range from port 49152 to port 65535, inclusive. However,the ports may use only some of this range (and the used portions may ormay not be contiguous) and/or the ports may include ports in any otherrange such as, for example, Well Defined Ports (ranging from port 0 toport 1023) and/or Registered Ports (ranging from port 1024 to port49151).

The request servicer 310 of the illustrated example receives therequests from the request and response ports 305 and performs a porttranslation. A port translation may not be necessary in the event thatthe proxy is hosted via the same port that the requested content ishosted on. For example, if the proxy is hosted on port 80 and thecontent request is for content provided on port 80 (e.g., HTTP content),no port translation would occur. First, the request is inspected todetermine the destination port that is intended for communication withthe Internet content provider 170. For example, in many situations, therequest will be for HTTP content and the destination port will beidentified as port 80. However, any other destination port may beemployed. For example, FTP traffic may be translated to port 21. Thecontent gatherer 320 is responsible for gathering the content identifiedin the request (e.g., by sending translated requests to thecorresponding content provider). Once the content is gathered, therequest servicer 310 performs another port translation on the receivedcontent response to generate a translated response and to send thetranslated response to the client device over the port assigned to theclient device that made the request.

The Internet content processor 315 of the illustrated example determinesthe port (e.g., port 50,000) that the request was received on, andstores the request in the storage database 160 in association with theport to uniquely identify the client device. Additionally oralternatively, the Internet content processor 315 may use the portnumber to determine and store the panelist ID and/or the client deviceID that was generated by the registrar 155 upon registration. In theillustrated example, the Internet content processor 315 stores therequest for content. However, the Internet content processor 315 maystore less than the entire request, a symbol for the request, etc., asshown in the tables of FIG. 3. Additionally or alternatively, theInternet content processor 315 may store the content provided in theresponse and/or segments and/or portions of the content provided in theresponse in the storage database 160. For example, the Internet contentprocessor 315 may store advertisements transmitted to the client devicein the storage database 160.

The content gatherer 320 of the illustrated example requests the contentidentified by the request for Internet content. In particular, thecontent gatherer 320 utilizes the Internet address of the contentrequested in the request via one of the ports 305 to generate a secondrequest to gather the requested Internet content. The content gatherer320 transmits the second request via the Internet port 325. The Internetport 325 of the illustrated example is a Transmission Control Protocol(TCP) port and/or a User Datagram Protocol (UDP) port. However, anyother port-based system may additionally or alternatively be used. TheInternet port of the illustrated example is for HTTP traffic (e.g., port80). However, any other port may be used. For example, port 21 could beused for File Transfer Protocol (FTP) traffic.

While an example manner of implementing the proxy 165 of FIG. 1 has beenillustrated in FIGS. 1 and 3, one or more of the elements, processes,and/or devices illustrated in FIG. 3 may be combined, divided,re-arranged, omitted, eliminated, and/or implemented in any other way.Further, the request and response ports 305, the request servicer 310,the Internet content processor 315, the content gatherer 320, theInternet port 325 and/or, more generally, the example proxy 165 of FIG.3 and/or the example registrar 155 of FIG. 1 may be implemented byhardware, software, firmware, and/or any combination of hardware,software, and/or firmware. Thus, for example, any of the example requestand response ports 305, the example request servicer 310, the exampleInternet content processor 315, the example content gatherer 320, theexample Internet port 325 and/or, more generally, the example proxy 165could be implemented by one or more circuit(s), programmableprocessor(s), application specific integrated circuit(s) (ASIC(s)),programmable logic device(s) (PLD(s)) and/or field programmable logicdevice(s) (FPLD(s)), etc. When any of the appended apparatus claims areread to cover a purely software and/or firmware implementation, at leastone of the example request and response ports 305, the example requestservicer 310, the example Internet content processor 315, the examplecontent gatherer 320, the example Internet port 325, the example proxy165, the example registrar 155, and/or the storage database 160 arehereby expressly defined to include hardware and/or a computer readablemedium such as a memory, DVD, CD, etc. storing the software and/orfirmware. Further still, the example proxy 165 of FIGS. 1 and 3 mayinclude one or more elements, processes, and/or devices in addition to,or instead of, those illustrated in FIG. 3, and/or may include more thanone of any or all of the illustrated elements, processes, and devices.

A flowchart representative of example machine-readable instructions forimplementing the proxy 165 of FIGS. 1 and/or 3 is shown in FIG. 4.Further, a flowchart representative of example machine-readableinstructions for implementing the registrar 155 of FIG. 1 is shown inFIG. 5. In these examples, the machine-readable instructions compriseprogram(s) for execution by a processor such as the processor 712 shownin the example computer 700 discussed below in connection with FIG. 7.The program may be embodied in software stored on a computer readablemedium such as a CD-ROM, a floppy disk, a hard drive, a digitalversatile disk (DVD), or a memory associated with the processor 712, butthe entire program(s) and/or parts thereof could alternatively beexecuted by a device other than the processor 712 and/or embodied infirmware or dedicated hardware. Further, although the example program(s)are described with reference to the flowcharts illustrated in FIGS. 4and 5, many other methods of implementing the example proxy 165 and/orthe example registrar 155 may alternatively be used. For example, theorder of execution of the blocks may be changed, and/or some of theblocks described may be changed, eliminated, or combined.

As mentioned above, the example processes of FIGS. 4 and 5 may beimplemented using coded instructions (e.g., computer-readableinstructions) stored on a tangible computer readable medium such as ahard disk drive, a flash memory, a read-only memory (ROM), a compactdisk (CD), a digital versatile disk (DVD), a cache, a random-accessmemory (RAM) and/or any other storage media in which information isstored for any duration (e.g., for extended time periods, permanently,brief instances, for temporarily buffering, and/or for caching of theinformation). As used herein, the term tangible computer-readable mediumis expressly defined to include any type of computer readable storageand to exclude propagating signals. Additionally or alternatively, theexample processes of FIGS. 4 and 5 may be implemented using codedinstructions (e.g., computer-readable instructions) stored on anon-transitory computer-readable medium such as a hard disk drive, aflash memory, a read-only memory, a compact disk, a digital versatiledisk, a cache, a random-access memory and/or any other storage media inwhich information is stored for any duration (e.g., for extended timeperiods, permanently, brief instances, for temporarily buffering, and/orfor caching of the information). As used herein, the term non-transitorycomputer-readable medium is expressly defined to include any type ofcomputer-readable medium and to exclude propagating signals.

FIG. 4 is a flowchart representative of example machine-readableinstructions 400 that may be executed to implement the example proxy ofFIGS. 1, 2, and 3. The program of FIG. 4 begins at block 405, where theexample machine-readable instructions 400 begin execution. First, therequest servicer 310 of the proxy 165 waits for content requests (block405). In the illustrated example, the request servicer 310 waits forcontent requests only on ports assigned to a client. However, therequest servicer 310 may wait for content requests on any or all ports.Additionally, the request servicer 310 may inspect the Internet Protocol(IP) address against known range(s) of IP addresses to determine if therequest should be serviced. For example, the known range of IP addressmay include ranges of IP addresses which are assigned to a particularInternet service provider and/or carrier. This may, for example,restrict use of the proxy 165 to mobile devices. If the request servicer310 determines that the request did not originate from an IP addresswithin the particular Internet service provider, the request servicer310 may ignore the request.

Next, the request servicer 310 receives a content request on a port.Because multiple requests for content may be received at substantiallythe same time, the proxy 165 may receive a first content request on afirst port (block 410) and a second content request on a second port(block 430). In the illustrated example, the content requests areprocessed in parallel to decrease the amount of time taken to respond torequests. However, the content requests may be processed in any othermanner. For example, the content requests may be processed serially. Theparallel processing of any number of requests is represented in FIG. 4by these dots “•••”.

Next, the content gatherer 320 generates second request(s) based oncorresponding ones of the request received at blocks 410 and 430, toretrieve the Internet content identified in the corresponding contentrequests (blocks 415 and 435). The content gatherer 320 gathers therequested Internet content by sending the second requests via theInternet port 325. In the illustrated example, port 80 is used forsending requests. However, any other port may additionally oralternatively be used.

The Internet content processor 315 also associates the content requestswith the corresponding requesting device and stores the association inthe storage database (blocks 420 and 440). In the illustrated example,the Internet content processor 315 associates the first content requestwith the corresponding client device using the port number that therequest was received upon. Since each port is used only by a singleclient device, each client device can be uniquely identified based onthe port number of the port on which a request is received. Further,when storing the association in the storage database 160, the Internetcontent processor 315 may store one or more identifier(s) of the port,the client device, the panelist, etc. Additionally, the Internet contentprocessor 315 may store the returned content or a portion of thereturned content in the storage database 160 (block 420, 440).

The Internet content processor 315 may filter what is stored in thestorage database. For example, the Internet content processor 315 mayonly store content requests that request HTTP content, as requests fornon-HTTP content may not be parsed properly when analyzing theinformation. As another example, the Internet content processor 315 mayomit style content (e.g., cascading style sheet (CSS) documents) frombeing stored in the storage database 160, as style content may be oflimited use when analyzing the information.

The request servicer 310 finishes servicing the request from the clientdevice by transmitting the requested Internet content to the clientdevice via the port on which the content request was received (blocks425 and 445). Control returns to the block 405, where the requestservicer 310 waits for more content requests (block 405).

FIG. 5 is a flowchart representative of example machine-readableinstructions 500 that may be executed to implement the example registrar155 of FIG. 1. The example machine-readable instructions 500 of FIG. 5begin execution at block 503, where the panelist 115, 135 submitsregistration data to the registrar 155 (block 503). In the illustratedexample, the registration data is received by the registrar 155 (block505) via an electronic interface (e.g., a website). However, theregistrar may receive the registration data in any other way. Forexample, the registrar may receive the registration data via a telephoneinterface, direct mailings, predefined lists, etc.

Next, the registrar 155 assigns the panelist a unique port (block 510).In the illustrated example, the unique port is within the Dynamic and/orPrivate Port range as defined by IANA (e.g., port 49152 through 65535).However, any other port number in any other range may alternatively beused. In the illustrated example, because ports are assigned on a onepanelist to one port basis, the port number functions as a uniqueidentifier for the client device and/or the panelist.

The registrar 155 generates a configuration file (block 515). Theconfiguration file includes the unique port assigned to the clientdevice of the panelist, and an Internet proxy address. The Internetproxy address is the address of the proxy 165. The port number is a portof the proxy 165 and is uniquely associated with the panelist. In theillustrated example, the configuration document is an Extensible MarkupLanguage (XML) file implementing a property list (plist) file comprisingconfiguration data including the port number and the Internet proxyaddress. However, any other type of document may be generated such as,for example, a comma separated (CSV) document, a portable documentformat (PDF) document, a Microsoft® Word® document, etc. In theillustrated example, the configuration document is signed using apublic/private key infrastructure. However, the configuration mayalternatively not be signed. If the configuration document is notsigned, it may appear as an invalid configuration file to the panelist,which may cause the panelist to abandon participation in the panel.

Next, the registrar 155 transmits the configuration file to the clientdevice (block 520). In the illustrated example, the configuration fileis transmitted via an electronic mail (email) message. The email messageincludes a hyperlink that may be selected to download the configurationfile. However, any other methods of transmitting the configuration filemay additionally or alternatively be used. For example, theconfiguration file may be transmitted as an attachment to the emailmessage, the registrar 155 may transmit a short message service (SMS)message comprising an Internet address where the client device maydownload the configuration file, a direct mailing may be sent to thepanelist comprising the instruction document and/or additionallycomprising an electronic medium containing the configuration file, atelephone call may be placed to orally instruct the panelist on how toconfigure the client device, etc. The panelist and/or client device thenreceives the configuration file (block 523).

The client device 110, 130 is then configured via the configuration file(block 525). Since the configuration file is an electronic document thatmay be interpreted by the client device 110, 130, the client devicereceives the transmitted configuration file and automatically appliesthe settings contained in the document such that further Internetrequests originating with the client are addressed to the correspondingport of the proxy 165. However, the configuration file may additionallyor alternatively include an instruction document that may guide thepanelist on how to configure the client device. The instruction documentmay thereby instruct the panelist on how to apply the configuration fileor may instruct the panelist on how to manually apply the data in theconfiguration file.

Upon application of the data contained in the configuration file,subsequent requests for Internet content made by the client device 110,130 are routed according to the configuration file. In particular, sincethe configuration file includes the Internet proxy address and theunique port number assigned to the client device, requests are proxiedthrough the Internet proxy address via the unique port number.

FIG. 6 illustrates an example configuration file 600 that may begenerated by the example registrar 155 of FIG. 1. The exampleconfiguration file 600 includes configuration data 605. Theconfiguration data 605 include an Internet proxy address 610 and aunique port assignment 615.

The configuration file 600 is an Extensible Markup Language (XML) fileimplementing a property list (plist) file including configuration datasuch as the port number and the Internet proxy address of the proxy 165.However, any other type of document may be generated such as, forexample, a comma separated (CSV) document, a portable document format(PDF) document, a Microsoft® Word® document, etc. The configuration fileis implemented as a plist file in the illustrated example to facilitatesupport for an Apple® iPhone® as the mobile device. However, any othermobile device may additionally or alternatively be used, and the mobiledevice may implement any other operating system (e.g., Google® Android,Windows® Mobile®, etc.). For example, the configuration file may beformatted differently or may be in a different format to supportinterpretation by client devices implementing an operating system otherthan the operating system implemented by the Apple® iPhone®.

FIG. 7 is a block diagram of an example computer 700 capable ofexecuting the instructions of FIGS. 4 and 5 to implement the monitoringsystem of FIG. 1. The computer 700 can be, for example, a server, apersonal computer, or any other type of computing device.

The system 700 of the instant example includes a processor 712. Forexample, the processor 712 can be implemented by one or more Intel®microprocessors from the Pentium® family, the Itanium® family or theXScale® family. Of course, other processors from other families are alsoappropriate.

The processor 712 is in communication with a main memory including avolatile memory 718 and a non-volatile memory 720 via a bus 722. Thevolatile memory 718 may be implemented by Synchronous Dynamic RandomAccess Memory (SDRAM), Dynamic Random Access Memory (DRAM), RAMBUSDynamic Random Access Memory (RDRAM) and/or any other type of randomaccess memory device. The non-volatile memory 720 may be implemented byflash memory and/or any other desired type of memory device. Access tothe main memory 714 is typically controlled by a memory controller (notshown).

The computer 700 also includes an interface circuit 724. The interfacecircuit 724 may be implemented by any type of interface standard, suchas an Ethernet interface, a universal serial bus (USB), and/or a PCIexpress interface.

One or more input devices 726 are connected to the interface circuit724. The input device(s) 726 permit a user to enter data and commandsinto the processor 712. The input device(s) can be implemented by, forexample, a keyboard, a mouse, a touchscreen, a track-pad, a trackball,isopoint and/or a voice recognition system.

One or more output devices 728 are also connected to the interfacecircuit 724. The output devices 728 can be implemented, for example, bydisplay devices (e.g., a liquid crystal display, a cathode ray tubedisplay (CRT), a printer and/or speakers). The interface circuit 724,thus, typically includes a graphics driver card.

The interface circuit 724 also includes a communication device (e.g.,the request servicer 310) such as a modem or network interface card tofacilitate exchange of data with external computers via a network (e.g.,an Ethernet connection, a digital subscriber line (DSL), a telephoneline, coaxial cable, a cellular telephone system, etc.).

The computer 700 also includes one or more mass storage devices 730 forstoring software and data. Examples of such mass storage devices 730include floppy disk drives, hard drive disks, compact disk drives, anddigital versatile disk (DVD) drives. The mass storage device 730 mayimplement the storage database 160.

The coded instructions 732 of FIGS. 4 and 5 may be stored in the massstorage device 730, in the volatile memory 718, in the non-volatilememory 720, in the local memory 714, and/or on a removable storagemedium such as a CD or DVD.

From the foregoing, it will be appreciated that example methods,apparatus and articles of manufacture have been disclosed which allowInternet content requests made from mobile devices without requiringauthorization credentials while still uniquely identifying therequesting device and/or panelist irrespective of whether the requestoriginated with a browser or an application accessing Internet content.

Although certain example methods, apparatus, and articles of manufacturehave been described herein, the scope of coverage of this patent is notlimited thereto. On the contrary, this patent covers all methods,apparatus, and articles of manufacture fairly falling within the scopeof the claims of this patent.

What is claimed is:
 1. A system to monitor media access by a mobiledevice, the system comprising: at least one processor; and memoryincluding instructions that, when executed, cause the at least oneprocessor to: in response to obtaining first panelist demographicinformation associated with a first panelist and second panelistdemographic information associated with a second panelist, assign afirst port of a proxy server to a first mobile device associated withthe first panelist and a second port of the proxy server to a secondmobile device associated with the second panelist, the first portdifferent from the second port; transmit configuration information tothe first mobile device to instruct the first mobile device to transmitrequests for media including a first request to the first port; and inresponse to obtaining the first request at the first port, store anassociation between the first panelist demographic information and themedia.
 2. The system of claim 1, wherein the instructions, whenexecuted, cause the at least one processor to service the first requestby: transmitting the first request from a third port of the proxyserver, the third port in communication with the Internet, the firstport different from the third port, the first port not in communicationwith the Internet; receiving the media at the third port; andtransmitting the media from the first port to the first mobile device.3. The system of claim 1, wherein the association is a firstassociation, and the instructions, when executed, cause the at least oneprocessor to: register the first mobile device by storing a secondassociation between the first mobile device, the first port, and thefirst panelist demographic information; in response to the first portreceiving the first request, identify the first mobile device as havingrequested the media based on the second association; in response to athird port different from the first port obtaining the media, associatethe first request with the first mobile device; and associate the firstpanelist demographic information with at least one of the media or thefirst request based on the first association.
 4. The system of claim 1,wherein the instructions, when executed, cause the at least oneprocessor to not service the first request if the first requestoriginated from an Internet Protocol (IP) address outside of an IPaddress range known to originate media requests from mobile devices, theIP address range being a range of IP addresses that represents deviceson a cellular network.
 5. The system of claim 1, wherein theinstructions, when executed, cause the at least one processor to obtainthe first panelist demographic information and the second panelistdemographic information during a panelist registration process, at leastone of the first panelist demographic information or the second panelistdemographic information including at least one of an employment status,a gender, a marital status, or a race.
 6. The system of claim 1, whereinthe first port functions as a unique identifier for at least one of thefirst mobile device or the first panelist, and the instructions, whenexecuted, cause the at least one processor to only assign the first portto the first mobile device.
 7. The system of claim 1, wherein the proxyserver includes a plurality of ports including the first port and thesecond port, and the instructions, when executed, cause the at least oneprocessor to assign a plurality of mobile devices including the firstmobile device and the second mobile device on a one-to-one port basis,the first mobile device of the plurality of the mobile devices to onlybe assigned the first port.
 8. A non-transitory computer readablestorage medium comprising instructions that, when executed, cause atleast one processor to: in response to obtaining first panelistdemographic information associated with a first panelist and secondpanelist demographic information associated with a second panelist,assign a first port of a proxy server to a first mobile deviceassociated with the first panelist and a second port of the proxy serverto a second mobile device associated with the second panelist, the firstport different from the second port; transmit configuration informationto the first mobile device to instruct the first mobile device totransmit requests for media including a first request to the first port;and in response to obtaining the first request at the first port, storean association between the first panelist demographic information andthe media.
 9. The non-transitory computer readable storage medium ofclaim 8, wherein the instructions, when executed, cause the at least oneprocessor to service the first request by: transmitting the firstrequest from a third port of the proxy server, the third port incommunication with the Internet, the first port different from the thirdport, the first port not in communication with the Internet; receivingthe media at the third port; and transmitting the media from the firstport to the first mobile device.
 10. The non-transitory computerreadable storage medium of claim 8, wherein the association is a firstassociation, and the instructions, when executed, cause the at least oneprocessor to: register the first mobile device by storing a secondassociation between the first mobile device, the first port, and thefirst panelist demographic information; in response to the first portreceiving the first request, identify the first mobile device as havingrequested the media based on the second association; in response to athird port different from the first port obtaining the media, associatethe first request with the first mobile device; and associate the firstpanelist demographic information with at least one of the media or thefirst request based on the first association.
 11. The non-transitorycomputer readable storage medium of claim 8, wherein the instructions,when executed, cause the at least one processor to not service the firstrequest if the first request originated from an Internet Protocol (IP)address outside of an IP address range known to originate media requestsfrom mobile devices, the IP address range being a range of IP addressesthat represents devices on a cellular network.
 12. The non-transitorycomputer readable storage medium of claim 8, wherein the instructions,when executed, cause the at least one processor to obtain the firstpanelist demographic information and the second panelist demographicinformation during a panelist registration process, at least one of thefirst panelist demographic information or the second panelistdemographic information including at least one of an employment status,a gender, a marital status, or a race.
 13. The non-transitory computerreadable storage medium of claim 8, wherein the first port functions asa unique identifier for at least one of the first mobile device or thefirst panelist, and the instructions, when executed, cause the at leastone processor to only assign the first port to the first mobile device.14. The non-transitory computer readable storage medium of claim 8,wherein the proxy server includes a plurality of ports including thefirst port and the second port, and the instructions, when executed,cause the at least one processor to assign a plurality of mobile devicesincluding the first mobile device and the second mobile device on aone-to-one port basis, the first mobile device of the plurality of themobile devices to only be assigned the first port.
 15. An apparatus tomonitor media access by a mobile device, the apparatus comprising: meansfor obtaining, from a panelist during a panelist registration process,panelist demographic information identifying a demographic of thepanelist; means for assigning, in response to the obtaining of thepanelist demographic information, a first port of a virtual interface ofa proxy server to the mobile device associated with the panelist, themobile device to transmit requests for media to the first port, therequests for media to identify the first port in a header of therequests; means for transmitting configuration information to the mobiledevice, the configuration information to instruct the mobile device totransmit future requests for media to the first port; means foridentifying, in response to receiving a first request for media from themobile device at the first port, the panelist identification informationassociated, by the assigning, with the first port receiving the firstrequest for the media, the proxy server to service the first request bytransmitting the first request from a second port of the proxy serverand receiving the media at the second port, the second port incommunication with the Internet, the first port different from thesecond port; and means for storing, monitoring data indicating thepanelist having the demographic requested the media.
 16. The apparatusof claim 15, wherein the means for transmitting is first means fortransmitting, and further including second means for transmitting therequested media to the mobile device via the first port.
 17. Theapparatus of claim 15, wherein the means for storing is to store thefirst request for the media in a database.
 18. The apparatus of claim15, wherein the means for storing is to store the requested media in adatabase.
 19. The apparatus of claim 15, further including means forservicing to not service the first request for the media from non-mobiledevices if the first request originated from an Internet Protocol (IP)address outside of an IP address range known to originate media requestsfrom mobile devices.
 20. The apparatus of claim 19, wherein the IPaddress range is a range of IP addresses representing devices on acellular network.